System and method for an on-line jurisdiction manager

ABSTRACT

The jurisdiction online manager manages required jurisdictional inspections mandated by a plurality of different jurisdictions performed by non-governmental entities. A central computer system receives object data for an object and most other information via a global computer network, typically the Internet. Based upon the provided object data, the jurisdiction online manage can determine the controlling jurisdiction for the object. The controlling jurisdiction is the jurisdiction in which the object is located. After determining the controlling jurisdiction, the jurisdiction&#39;s inspection form or a similar inspection template can be provided to the inspectors, who will perform the actual physical inspections of the objects. After receiving inspection result data from the non-governmental inspection, the inspection result data is stored the system database. The inspection result data is then provided to the controlling jurisdiction. The controlling jurisdiction reviews the result data online and result data is provided to the inspection entity.

CROSS REFERENCE TO RELATED APPLICATIONS

The following Patent Application claims priority to the U.S. ProvisionalApplication No. 60/231,165 entitled “Jurisdiction On-line” filed on Sep.7, 2000.

This is a continuation of application Ser. No. 09/948,200, filed Sep. 7,2001, now U.S. Pat. No. 7,181,304, which is incorporated herein byreference, and is also related to application Ser. No. 11/624,939 filedJan. 19, 2007.

TECHNICAL FIELD

The invention relates generally to the field of network-based servicesand, more particularly, to a jurisdiction online management system thatmanages required inspections mandated by a plurality of differentjurisdictions performed by non-governmental entities.

BACKGROUND OF THE INVENTION

The industrial revolution was made possible by the invention of manydifferent types of machines and other complicated equipment. Onesignificant invention, the boiler, provided the means to convert waterin steam, which is still used to power selected motors and to heatmixtures. Modem boilers include many different types of vessels used toheat water, hydrocarbons, and other liquids. These boilers range fromsimple residential water heaters to complicated oil refinery crackingtowers.

In addition, the pressure vessel enabled the evolution of sophisticatedchemical processes that must take place under high pressure or undervacuum. Pressure vessels became increasingly important as ourunderstanding of chemistry and chemical reactions grew. Today, pressurevessels are used in the production processes of virtually everymanufacturing industry.

As a consequence of their usefulness, pressure vessels and boilers havebecome relatively common equipment. In fact, a large university canhouse over 900 of these objects. The prevalence of these objects alongwith the inherent associated danger mandate that these objects bemanufactured and operated safely.

In the 1800s, boiler and pressure vessel explosions were common. Severalexplosions that resulted in significant loss of life prompted theadoption of codes that dictated the design specifications andperformance requirements for new equipment. Gradually various states,municipalities, and other jurisdictions adopted these codes and mandatedthe continued evaluation and inspection of existing equipment. Most ofthese jurisdictions established laws to enforce the codes.

In most states, the laws specified that the insurance company coveringthe equipment against property loss must provide licensed inspectors toexamine the equipment and report the inspection results to thejurisdiction. Obviously, the insurance companies have a vested interestin assuring the safe operation of these objects. Government inspectorsperform the inspections and reporting tasks on non-insured equipment.The frequency of these inspections is based upon the size and type ofthe vessel and can vary from twice per year to once every three years.

The current process for reporting the inspections is done with paperforms supplied by the jurisdiction in which the vessel is located. Anadministrator at the insurance company manages the active policies,which have boiler and pressure vessel coverage. The administratordetermines the inspections' due dates and allocates the inspectionsamong the company's inspectors authorized in the subject jurisdiction.The administrator copies and to sends the inspector the form orinformation from the prior years, if available. The inspector makes theinspection, fills out the form, and sends it to the designated officewithin the insurance company. The designated office makes a copy andforwards the original to the appropriate jurisdictional department forreview.

Each insurance company has a multiple forms arriving each day from itsinspectors. The home office personnel must determine which forms go towhich jurisdictions, which files get which copies, and track down thefiles, etc. Approximately 15% of the inspections are not approved by thejurisdiction upon the first review. The jurisdictional reviewer willnote the changes required and transmit the form back to the insurancecompany. The insurance company routes the transmittal back to theinspector, who completes the work in a manner acceptable by thejurisdiction. Upon acceptance of the inspection, the jurisdiction grantsa certificate of compliance.

The paper flow method is very cumbersome, time consuming, inefficient,and involves many steps. The process has a high cost related to thesubmission of inspection data including the costs associated themailings, filings, routing, reviews, and lost paperwork. The currentpractices generally results in many inefficiencies such as multiple dataentry and non-optimal scheduling of upcoming inspections. Furthermore,the current system has significant costs associated with inaccurate dataresulting in late inspections and multiple revisits.

The aforementioned problems are further compounded when a companyswitches insurance carriers. In this situation, the insurance companydoes not have access to historical data and begins building its ownseparate files. The lack of historical data dramatically increases thechances for the need for a re-inspection. In addition, all backgroundinformation must be collected and re-entered, which increase the odds ofpoor data. Due to the competitive nature of the insurance business,companies may switch insurance carriers on a non-infrequent basis.

Several solutions have been attempted to solve some of the problemsassociated with the paper transfer process. Some states have tried todevelop their own jurisdictional software. However, there exists over 60regulated jurisdictions including states, municipalities, and Canadianprovinces. In this situation, many difficulties arise because there isnot a common insurance company interface or program. It would beextremely expensive and difficult for the insurance companies to supportand maintain the multitude of interfaces required. In addition, userinterface for the inspectors will not be consistent. Cross-companyreporting would be extremely difficult. Furthermore, it is expensive foreach jurisdiction to develop, roll out, and maintain separate softwareprograms.

Another option is electronic jurisdiction interfaces. Clearly, thismethod is extremely costly for each entity to develop their ownsoftware. Except for the largest insurance carriers, the cost may beprohibitive. Insurance companies would have to support up to 67different formats, which could be worse than a paper system. Inaddition, the jurisdictions will be slow to embrace the process, makingit terribly inefficient and expensive until a substantial majority ofthe jurisdictions allow the process. Further complicating the process isthe variable domains and data fields required by each differentjurisdiction. It is extremely unlikely that the jurisdiction will agreeon common data types and domains. Additionally, flat data files arenon-hierarchical in nature, which can create update difficulties.Clearly, the data transfer is not-in real time and any workflow supportwould be minimal. Moreover, in an electronic data transfer system,additional features are not easy to add. In addition, many governors aremandating web applications for governmental functions.

Clearly, a need exists for an efficient, economical process for thetransfer of information between jurisdictions and the entities that aremandated to perform required activities.

SUMMARY OF THE INVENTION

The present invention meets the needs described above in a jurisdictiononline manager. The system provides an efficient, centralized, and webenabled process for the transfer of data between multiple jurisdictionsand multiple entities required to routinely interact with the multiplejurisdictions. The system manages required inspections mandated by aplurality of different jurisdictions performed by non-governmentalentities. The system is applicable to pressure vessels, boilers,elevators, amusement park rides, and other required jurisdictionalinspections of objects.

The system provides a central staging database for data. Consequentlyall insurance company have a common interface and programs to supporttheir mandated inspection functions. Hence, the inspectors have only oneuser interface with which to cope. In addition, the jurisdictions do nothave to agree on the types, domains, or any other information becausethe system supports multiple jurisdiction forms. Because thejurisdictions do not have to agree on standards or need to invest inexpensive development, the system should achieve early adoption by thejurisdictions.

The centralized system provides a hierarchical data structure thatallows for easy updates and reverse delta storage. Furthermore, thecentral system enables real time availability of current data. Moreover,data validation can be performed as well as enforceable data fields anddomains. Additionally, complete historical information about the storedobjects can be available online.

Generally speaking, the invention manages required inspections mandatedby a plurality of different jurisdictions performed by non-governmentalentities. A central computer system receives object data for an objectand most other information via a global computer network, typically theInternet. The object data is stored in a system database. Based upon theprovided object data, the jurisdiction online manager can determine thecontrolling jurisdiction for the object. The controlling jurisdiction isthe jurisdiction in which the object is located. After determining thecontrolling jurisdiction, the jurisdiction's inspection form or asimilar inspection template can be provided to the inspectors, who willperform the actual physical inspections of the objects. In most cases,non-governmental inspectors perform the inspections. These inspectorsgenerally work for inspection entities, usually insurance companies thatperform the mandated inspections in a plurality of differentjurisdictions.

After receiving inspection result data from the inspection, theinspection result data is stored the system database. The inspectionresult data is then provided to the controlling jurisdiction. Thecontrolling jurisdiction reviews the result data online and any reviewresult data is stored in the system database. The reviewed result datais provided to the inspection entity, which can view the results online.

The system can manage most aspects of the statutorily requiredinspections. Other aspects of the managed inspection process can includemanaging inspector commission information. The inspector commissionstatus can be verified prior to accepting inspection results by thatinspector. In addition, the system can manage payment information. Thesystem can receive payment information and verify object status prior toproviding issuance of an object certificate of compliance. Lack ofpayment or any current violations can block the issuance of a compliancecertificate. Furthermore, the system can perform scheduling functions.The system can automatically determine objects with upcoming inspectionsdue dates and provide this information to the inspection entity.Inspectors at the inspection entity can calendar the inspections asdesired.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram illustrating a jurisdiction onlinemanagement system.

FIG. 2 is a flow diagram illustrating an object inspection life cycle.

FIG. 3 is a functional block diagram illustrating a hardwarearchitecture for a jurisdiction online manager.

FIG. 4 is a functional block diagram illustrating a softwarearchitecture for a jurisdiction online manager.

FIG. 5 is a flow diagram illustrating an inspection routine.

FIG. 6 is a flow diagram illustrating a review routine.

FIG. 7 is a functional block diagram illustrating a databasearchitecture for a jurisdiction online manager.

FIG. 8 is a flow diagram illustrating a user interface routine.

FIG. 9 is a flow diagram illustrating an accounting interface routine.

FIG. 10 is a flow diagram illustrating an assignment interface routine.

FIG. 11 is a flow diagram illustrating an administration interfaceroutine.

FIG. 12 is a flow diagram illustrating a location interface routine.

FIG. 13 is a flow diagram illustrating an object interface routine.

FIG. 14 is a flow diagram illustrating an inspection interface routine.

FIG. 15 is a flow diagram illustrating a review interface routine.

FIG. 16 is a screen shot illustrating a user homepage.

FIG. 17 is a screen shot illustrating a location edit web page.

FIG. 18 is a screen shot illustrating a boiler edit web page.

FIG. 19 is a screen shot illustrating an inspection edit web page.

FIG. 20 is a screen shot illustrating a review changes web page.

FIG. 21 is a screen shot illustrating a review boiler edit web page.

DETAILED DESCRIPTION OF THE EMBODIMENTS

The described embodiment discloses a system that provides an efficientmanagement of the required regulatory inspections of boilers andpressure vessels in multiple jurisdictions. The jurisdiction onlinemanager (JOM) is designed to automatically provide the appropriatejurisdiction inspection data requirements and forms to commissionedinspectors from a plurality of insurance carriers. Although thedescribed embodiment refers to boiler and pressure vessel inspections,those skilled in art can readily appreciate that the system is equallyadvantageous in other scenarios involving multiple regulating agencieswhich do not perform the actual regulated function including inspectionsof elevators, amusement park rides, and the like.

The disclosed embodiment provides a cost-effective system for theperformance and jurisdictional review of boiler and pressure vesselinspections. The complexity of ensuring proper data nomenclature andformat required by each specific jurisdiction is solved by the isjurisdiction online manager. In addition, the system provides acomparison of changed information to facilitate efficient review of theinspection by the appropriate jurisdiction. The system also manages thepayment of proscribed fees and the issuance of certificates. Insummation, the jurisdiction online manager directs the inspectionprocess from installation of the object to the object's decommission.

Turning to the figures, in which like numerals indicate like elementsthroughout the several figures, FIG. 1 illustrates a jurisdiction onlinemanagement system 100 constructed in accordance with an embodiment ofthe present invention. The system 100 is connected for computercommunications via a known global computer network commonly known as theInternet 199. It is known in the art to send packets of information viathe Internet. One common protocol for the transfer of data via theInternet 199 is the Transfer Control Protocol Internet Protocol(TCP/IP).

The disclosed jurisdiction online management system 100 includes ajurisdiction online manager 110. The jurisdiction online manager 110stores object data, schedules inspections, provides the appropriatejurisdiction forms, accepts inspection data, provides inspection andrepair data for jurisdictional review, accepts repair information,accepts payment, provides inspection certificates, and provides otherfunctions which facilitate the boiler and pressure vessel inspectionprocess. A flow chart of the inspection process is illustrated inreference to FIG. 2. In addition, illustrations and flow chartsdescribing the jurisdiction online manager 110 constitute the remainingfigures.

Boilers and pressure vessels 150 are devices that operate underpressure. A boiler 150 generates steam by the application of energy, anda pressure vessel 150 contains pressure without the application ofenergy. Many facilities ranging from fast food restaurants anduniversities to industrial complexes utilize pressure vessels andboilers 150 during their normal operation. Objects 150 under pressurecan be dangerous if they are not properly maintained and operated.

Jurisdictions 120 are the regulatory entities that set the safetyrequirements and govern the issuance of certificates of compliance.Jurisdictions 120 are typically states, cities, or Canadian provinces.Each regulatory entity 120 has the authority to determine the requiredinspections and the inspection frequencies for pressure vessels andboilers 150 within their jurisdiction. In addition, each jurisdictionrequires the inspection information in its format utilizing itscategories and domains. Reviewers 125 at each jurisdiction 120 evaluateeach inspection, repair, and other data to ensure compliance with thejurisdiction's requirements. Upon acceptance of the inspection data, thejurisdiction 120 authorizes the issuance of a compliance certificatethat enables the object 150 to legally continue operating.

Insurance companies 130 provide insurance coverage for most pressurevessels and boilers 150. Since the insurance companies 130 have a vestedinterest in ensuring safe performance, the jurisdictions 120 havedelegated the responsibility of inspecting these objects 150 to theinsurer. The insurance companies 130 provide the inspectors 135 thatphysically travel to the object's location and perform the requiredinspections. An inspector 135 must be qualified by a jurisdiction 120and receive a commission in order to perform an inspection in thatjurisdiction 120. An inspector 135 can access the jurisdiction onlinemanager 110 via the Internet 199 and print an inspection form for thatjurisdiction prior to performing the inspection. Alternatively, theinspector 135 can enter the inspection data directly on-line through theuse of a portable computing device utilizing wireless applicationprotocol (WAP), or other suitable communication device.

FIG. 2 discloses a flow diagram of an object inspection life cycle 200.The life cycle begins at step 205 with the object's creation. An objectbuilt to ASME code standards can be registered with the Nation Board ofBoiler and Pressure Vessel Inspectors. Registration is legally requiredin most National Board Member jurisdictions. After an object isinstalled, the object requires an inspection.

Step 205 is followed by step 210, in which a physical inspection isscheduled. Some jurisdictions require that the initial inspection mustbe performed by the jurisdiction. Other jurisdictions allow theinsurance carrier to perform the inspection. In any event, all pressurevessels and boilers are required to receive a physical inspection afterinstallation.

Step 210 is followed by step 215 in which the physical inspection isperformed. Inspections must be performed by an inspector commissioned toperform inspections in that particular jurisdiction. The commissionedinspector travels to the installation site and performs a physicalinspection. Each jurisdiction may require recordation of different data,may have different domains, and may have diverse object categories.

Step 215 is followed by step 220, in which the inspector determineswhether to issue a violation or make a recommendation. Examples ofvolitions include insufficient combustion air available for a boiler,improperly set safety valve, or unsuitable clearance. A recommendationis a non-mandatory suggestion to improve the safety of the object. If noviolations or recommendations have been cited, the NO branch of step 220is followed to step 240, in which the jurisdiction performs a review. Ifa violation or recommendation has been cited, the YES branch of step 220is followed to step 225, in which the inspector determines if the citedproblem is certificate blocking.

If the cited problem is not certificate blocking, the NO branch of step225 is followed to step 240. If the cited problem is certificateblocking, the YES branch of step 225 is followed to step 230, in whichthe owner arranges for repair the object. If the object is not repaired,the NO branch of step 230 is followed to step 230, in which the ownerarranges for repair. Violations must be rectified before thejurisdiction will allow the object to be placed into service. Afterarranging for repairs, the YES branch of step 230 is followed by step235, in which an authorized repairer makes the necessary changes tobring the object within specifications. Step 235 is followed by 240.

In step 240, the jurisdiction reviews the inspection data and anyresultant repairs. Reviewers within the jurisdiction review any repairsand inspections to ensure compliance with the jurisdiction requirementsand ensure the validity of the data submitted. Step 240 is followed bystep 245, in which the reviewer determines to accept the inspection andany associated repairs. If the inspection is not accepted, the NO branchof step 245 is followed to step 210 for inspection of the repairs orreinspection because of conflicting data. If the inspection is acceptedby the reviewer, the YES branch of step 245 is followed to step 250.

In step 250, the owner makes the requisite fee payment. Step 250 isfollowed by step 255 wherein upon receipt of the fee, a certificate forthe object is issued. Step 255 is followed by step 260, wherein theowner decides whether the object will be decommissioned. If the objectis not to be decommissioned, the NO branch of step 260 is followed tostep 205, in which the next inspection is scheduled. Each jurisdictionhas the authority to set the inspection schedule required for anyobject. If the object is to be decommissioned, the YES branch of 260 isfollowed, the object is decommissioned, no further inspection arerequired, and the inspection life cycle is completed.

FIG. 3 discloses a hardware architecture of the jurisdiction onlinemanager 110 constructed in accordance with an embodiment of the presentinvention. As will be understood in the art, the system is constructedutilizing Internet-enabled computer systems with computer programsdesigned to carry out the functions described herein. The computerprograms are executed on computer systems constructed as described inreference to FIG. 3. Although the disclosed embodiments are generallydescribed in reference to Internet is accessible computers, thoseskilled in the art will recognize that the present invention can beimplemented in conjunction with other program units for other types ofcomputers.

The disclosed embodiment of the present invention is implemented in adistributed computing environment such as the Internet. In a distributedcomputer environment, program units may be physically located indifferent local and remote memory storage devices. Execution of theprogram units may occur locally in a stand-alone manner or remotely in aclient server manner. By way of illustration and not limitation,distributed computing environments include local area networks (LAN) ofan office, enterprise-wide area networks (WAN), and the global Internet(wired or wireless connections). Accordingly, it will be understood thatthe terms computer, operating system, and application program includeall types of computers and the program units designed to be implementedby the computers.

The discussion of methods that follows, especially in the flow charts,is represented largely in terms of processes and symbolicrepresentations of operations by conventional computer components,including a central processing unit (CPU), memory storage devices forthe CPU, connected display devices, and input devices. Furthermore,these processes and operations may utilize conventional computercomponents in a heterogeneous distributed computing environment,including remote file servers, remote computer servers, and remotememory storage devices. Each of these conventional distributed computingcomponents is accessible by the CPU via a communication network.

The processes and operations performed by the computer include themanipulation of signals by a CPU, or remote server such as an Internetweb site, and the maintenance of these signals within data structuresreside in one or more of the local or remote memory storage devices.Such data structures impose a physical organization upon the collectionof data stored within a memory storage device and represent specificelectrical, optical, or magnetic elements. These symbolicrepresentations are the means used by those skilled in the art ofcomputer programming and computer construction to effectively conveyteachings and discoveries to others skilled in the art.

For the purposes of this discussion, a process is understood to includea sequence of computer-executed steps leading to a concrete, useful, andtangible result, namely, the effecting of the required inspections andreviews of boilers and pressure vessels in multiple jurisdictions.

These steps generally require manipulations of quantities such as ownerinformation data, location information data, scheduled dates, inspectiondata, review data, and other related information. Usually, though notnecessarily, these quantities take the form of electrical, magnetic, oroptical signals capable of being stored, transferred, combined,compared, or otherwise manipulated. It is conventional for those skilledin the art to refer to these signals as bits, bytes, words, values,elements, symbols, characters, terms, numbers, points, records, objects,images, files or the like. It should be kept in mind, however, thatthese and similar terms should be associated with appropriate quantitiesfor computer operations, and that these terms are merely conventionallabels applied to quantities that exist within and during operation ofthe computer.

It should also be understood that manipulations within the computer areoften referred to in terms such as displaying, deciding, storing,adding, comparing, moving, positioning, placing, and altering which areoften associated with manual operations performed by a human operator.The operations described herein include machine operations performed inconjunction with various input provided by a human operator or user thatinteracts with the computer. In addition, it will be understood that theprograms, processes, routines and methods described herein are notrelated or limited to any particular computer or apparatus, nor are theyrelated or limited to any particular communication network architecture.Rather, various types of general-purpose machines may be used withprogram units constructed in accordance with the teachings describedherein. Similarly, it may prove advantageous to construct a specializedapparatus to perform the method steps described herein by way ofdedicated computer systems in a specific network architecture withhard-wired logic or programs stored in nonvolatile memory, such as readonly memory.

With the foregoing in mind, the drawing figures starting with FIG. 4illustrate various functions, processes, or routines carried out by anembodiment of the present invention in which the disclosed jurisdictiononline management system 100 carries out the functions described inconnection with the flow charts and database maintenance. The functionsor processes in these figures are carried out in the disclosedembodiment of the present invention by software executing in computersassociated with the jurisdiction reviewers 125, insurance companyinspectors 135, and the jurisdiction online manager 110. Depending uponthe particular operation, the computers are connected for datacommunications via a network such as the Internet 199. It will also beunderstood that the processes and methods presented here may be arrangeddifferently, or steps taken in a different order. In other words, someprocesses and methods may be deleted, repeated, re-ordered, combined, orblended to form similar processes and methods.

Referring specifically now to FIG. 3, the principal hardware componentsof the JOM 110 include a tiered application architecture to distributedifferent applications components over different computers. Please notethat other embodiments may combine various application components ontothe same servers. Using multiple servers allows the JOM 110 to servicemultiple requests simultaneously and provides redundancy in case ofhardware failures.

The client tier, at which insurance company inspectors 135 andjurisdiction reviewers 125 interface with the jurisdiction onlinemanager 110, consists of inspector client computers 302 and reviewerclient computers 301. The client computers 305 run web browsingapplications that retrieve and display the jurisdiction online manager'sweb pages. The client computers 305 retrieve these web pages over aglobal computer network 199 such as the Internet. Web pages areaccessible over the Internet 199 by specifying in the web browserthe-page's unique identifier, known as a uniform resource locator (URL).A URL for a web page consists of the domain name or numeric address of aserver computer known as web server 320. When a particular web page isrequired, the client computer 305 makes a request over the Internet 199to a web server 320.

Internet communications with the JOM 110 are effected by an Internetfront end 310 that includes a router, a load balancer, and a firewall.The router is operative in the known manner to send and receive datapackets, typically in the form of TCP/IP packets commonly used forInternet communications. The load balancer operates in known manner tobalance the load from various communications amongst a plurality ofcomputers or servers that are employed to construct the JOM 110. Thedata packets pass through a firewall, which ensures the overall securityin a known manner before being passed to the web servers 320.

The web servers 320 include a plurality of redundant similarlyconfigured computers, two of which are illustrated, that are operativeto implement the front-end software. The web servers 320 are operativeto display information to users operating a web browser. The web servers320 also are operative to provide notifications in a known mannerusually via email. The web servers 320 are coupled to applicationservers 330.

The application servers 330 include a plurality of redundant similarlyconfigured servers, two of which are illustrated, that are operative toimplement the application is software. The application server containsthe logic that is used to determine which web pages are presented to theuser and how to respond to the user's actions. Screen shots of variousweb pages utilized by the users to interact with JOM 110 are illustratedin FIGS. 16-21. The application software also contains the necessarylogic necessary to process the user's transaction and provide theassociated updates and any notifications. The application software isdiscussed in greater detail in reference to FIG. 4. The applicationservers 330 are coupled to the web servers 320 and the database servers340.

The database servers 340 include a plurality of redundant similarlyconfigured servers, two of which are illustrated, that are operative tostore and retrieve information from a database 350. The database servers340 are coupled to the application servers 330. Further details of theinformation stored in the database 350 is provided in connection withFIG. 7.

FIG. 4 illustrates the principal software units or components of the JOM110 include a web interface 410, a location unit 420, an object unit425, an inspection unit 430, an accounting unit 435, an assignment unit440, a review unit 445, a view unit 450, an administration unit, and areport unit 460. Flow charts representing the user interface with theseunits are described in reference to subsequent FIGS. 8-15. The webinterface 410 is operative to receive communications via the Internet199. In particular, the web interface 410 provides Internet access foran insurer interface 411, a jurisdiction interface 412, an owner portal413, and a notification system 414. The web interface 411 providesaccess for the insurance company inspectors 135, jurisdiction reviewers125, and owners of the objects via a web browser. The web interface 121is also operative to receive electronic files, which can take the formof multiple dialogues including Electronic Data Interchange (EDI),Extensible Markup Language (XML), and custom flat file formats.

The notification system 414 is operative to send communications to usersof the JOM 110. The notification can be accomplished by an e-maildelivered via the Internet 199. Other notification means include anautomatically generated telephone call, a facsimile, a wirelesscommunication delivered via a wireless transmitter to a pager, mobilephone, or other wireless device, a wireless message delivery by wirelessapplication protocol (WAP) to a hand held computing device, or othersuitable methods for delivering messages.

The location unit 420 is operative to respond to communications,typically via a web browser, for the purpose of accepting or providinglocation information. Before allowing a user to modify or add locationinformation, the unit 420 ensures the user has the proper authority toperform these actions. Location information includes the locationphysical address, the company's name and contact information, billinginformation, the SIC code for the industrial application, and otherlocation related information. The unit 420 performs data entryvalidation checks to assist in elimination of input errors. In addition,the location unit 420 is operative to call the object unit 425 for theinput of object information and the inspection unit 430. The locationunit 420 assigns a unique location identifier for each separatelocation.

The object unit 425 is operative to respond to communications, typicallyvia a web browser, for the purpose of accepting or providing objectinformation. Before allowing a user to modify or add information, theunit 425 ensures the user has the proper authority to perform theseactions. Object information includes the jurisdiction number, themanufacturer assigned number, inspection information, location withinthe plant, year built, year installed, the object's use, means of fireand amount of energy input, capacity, safety relief information,insurance information, and other object related information. The unit425 performs data entry validation checks to assist in elimination ofinput errors. In addition, the object unit 425 is operative to call theinspection unit 425 for the input of inspection information and theassignment unit 430. The object unit assigns a unique identifier foreach separate object.

The inspection unit 430 is operative to respond to communications,typically via a web browser, for the purpose of accepting or providinginspection information. Before allowing a user to modify or addinspection information, the unit 430 ensures the user has the properauthority to perform these actions. Proper authority to conductinspections is an inspector commissioned by the jurisdiction in whichthe object is located. Inspection information includes the objectjurisdiction number, inspection date, status, inspector name, theoffending condition, the technical requirements, comments, and otherinspection related information. The unit 423 performs data entryvalidation checks to assist in elimination of input errors. In addition,the inspection unit 420 is operative to place the inspection in a queuefor a jurisdiction review.

The accounting unit 435 is operative to respond to communications,typically via a web browser, for the purpose of accepting or providingaccounting information. Before allowing a user to modify or add paymentinformation, the unit 435 ensures the user has the proper authority toperform these actions. Proper authority is a user authorized by theowner of the object to perform these functions. Accounting informationincludes payment information, object information, invoice information,and other payment related information. The unit 435 displays invoiceamounts, displays payment amounts, and is operative to allow paymentsfor selected objects. Upon payment and verification of acceptablestatus, the unit is operative to allow the provision of a certificate ofcompliance.

The assignment unit 440 operative to respond to communications,typically via a web browser, for the purpose of accepting or providingassignment information. Before allowing a user to access or modifyassignment information, the unit 440 ensures the user has the properauthority to perform these actions. The work assignment unitautomatically schedules inspection for objects with upcoming inspectiondue dates. The scheduled work assignment is operative to generate andplace the task in the insurance company scheduled inspection listing.Upon completion of an inspection or repair, request for variance, orother actions requiring jurisdiction review, the work assignment unit440 is operative to place the task in a review changes listing in thejurisdiction item task listing. Upon completion of a task, theassignment unit 440 removes the task from its respective task listing.

The review unit 445 is operative to respond to communications, typicallyvia a web browser, for the performance of a jurisdiction review. Beforeallowing a user to access review information, the unit 445 ensures theuser has the proper authority to perform these actions. Proper authorityto conduct reviews is a reviewer authorized by the jurisdiction toperform this function. The unit 445 is operative to display theinformation requiring a review, to display any changes in the reviewedinformation to assist in the review process and to accept comments. Uponacceptance of a review item, the item is deleted from a task listing.Upon rejection of the review, the owner is automatically notified andanother inspection is scheduled.

The administration unit 450 is operative to respond to communications,typically via a web browser, for the purpose of administrationfunctions. The administrative functions include adding and settingrights for other users, administrating system messages and safetybulletins, and tracking users. System message or safety bulletins areglobal messages that appear on user home pages. These messages can havethe scope of the insurance company users, jurisdiction employees,jurisdiction users, or system wide. The scope of control lo determinesthe scope of display. Additionally, the administration unit is operativeto add, delete, or edit users. The user information includes the user'spassword and user name, contact information, and the role the user canperform. The roles or groups determine the user's settings andpermissions. Typical user groups include chief inspector, data entry,accounting, work assignment, reviewer, and inspector. In addition, theadministration unit 450 is operative to set commissions. Commissionsdetermine in which jurisdictions a user can operate. The commissioninformation includes the commission number, the jurisdiction, along withstart and end date of the commission. An inspector's commission must bevalid for the JOM to authorize access to perform inspections.

According to an aspect of the invention, the computer programs describedabove collectively provide functions or components that form ajurisdiction online manager that provides a vastly improved system forthe performance in multiple jurisdictions of regulatory requiredfunctions by non-jurisdictional employees. Greater details of thesevarious functions and software components are described in subsequentFigures.

FIG. 5 illustrates an inspection routine process executed by the JOM.The process is initiated by step 505, wherein the JOM determines whethernew object information is to be entered. The determination is made bythe selection of add object in the location unit. If object informationis not to be entered, the NO branch of step 505 is followed to step 530,in which the JOM analyzes the database to determine those objectsrequiring scheduling of an inspection. If new object information hasbeen selected, the YES branch of step 505 is followed to step 510.

In step 510, the JOM determines if the user has the required permissionsto enter new object information. Permissions are set by theadministration unit described in reference to FIG. 4. If the user doesnot have the requisite permission setting, the NO branch of step 510 isfollowed to step 505, in which a determination is made as to whether theuser desires enter new object information. If the user does have therequisite permission setting, the YES branch of step 510 is followed tostep 515, in which the JOM receives the object information entered viathe user's web browser.

Step 515 is followed by step 520, in which the JOM performs errorchecking on the entered information. The user is prompted to verifyinputted information accuracy upon determination of a possible inputerror. After the error check process, the information is stored in theJOM database. Information storage in the database is described ingreater detail in reference to FIG. 7.

Step 520 is followed by step 525, in which the JOM schedules the objectfor an inspection. The JOM determines from the object information inwhich jurisdiction the object is located. Some jurisdictions perform allinitial inspections themselves. In these jurisdictions, a task will begenerated and placed in a task listing for that jurisdiction. Injurisdiction where the initial inspection will be performed by theinsurer, a task will be generated and placed in a task listing for thatinsurance company. Step 525 is followed by step 530.

In step 530, the JOM determines if any object requires inspections inthe near future. If no object requires an upcoming inspection, the NObranch of step 530 is followed to step 540, in which a determination ismade on whether a user desires to perform an inspection. If an objectrequires an upcoming inspection, the YES branch of step 530 is followedto step 535, in which the inspection is scheduled. The JOM computes therequired inspection based upon the last performed inspection and therequired inspection frequency. In step 535, a task is generated andplaced in a task listing for the covering insurance company for thoseobjects with upcoming required inspections. Step 535 is followed by step540.

In step 540, the JOM determines if a user desires to perform aninspection. Commissioned users on their homepages have a task listingwith a hot link to the individual objects requiring inspections.Additionally, an inspection can be requested via the inspection unitdescribed in reference to FIG. 4. If the user does not desire to performan inspection, the NO branch of step 540 is followed to step 505, inwhich the cycle is repeated. If the user desires to perform aninspection, the YES branch of step 540 is followed to step 545, in whichthe JOM determines if the user has a valid commission in thatjurisdiction.

In step 545, the JOM determines if the user has a valid commission inthat jurisdiction. Commission data is stored in reference to eachinspector. If the user does not have a valid commission, the NO branchis followed to step 540, in which the JOM determines if the user desiresto perform an inspection. If the user has a valid commission, the YESbranch is followed to step 550, in which the JOM determines the selectedobject. The user is able to select the individual objects that theinspector desires to perform an inspection.

Step 550 is followed by step 555, in which the JOM determines thejurisdiction in which the object resides. The jurisdiction informationis stored as a record in the JOM database. The information stored in thedatabase is described in greater detail in reference to FIG. 7. Step 555is followed by step 560, in which the JOM retrieves the inspectionformat lo for that jurisdiction. Each jurisdiction has its owncategories, domains, and required information. The JOM by utilizing thejurisdiction location data generates an appropriate inspection formbased upon that jurisdiction and the object to be inspected. Step 560 isfollowed by step 565 in which the JOM causes the proper jurisdictionform to be printed. Step 560 is followed by step 570.

In step 570, the JOM determines if the inspector desires to input theinspection information. If the inspector has not selected to inputinspection data, the NO branch of step 570 is followed to step 570, inwhich the JOM awaits for the inspection information to be inputted. Ifthe inspector has selected to input inspection data, the YES branch ofstep 570 is followed to step 575.

In step 575, the JOM receives the inspection information via interactionwith the inspector's web browser. Step 575 is followed by step 580, inwhich the JOM performs an error check on the inspection information. Theinspector is queried to verify any flagged possible inaccuracies. Step580 is followed by step 585.

In step 585, the submission of the inputted inspection information isdetermined. If the inspection is not to be submitted by the activationof the cancel button, the NO branch of step 585 is followed to step 540in which the JOM determines if the inspector desires to enter anotherinspection. If the inspection is to be submitted by the activation of asubmit button, the YES branch of step 585 is followed to step 590.

In step 590, the JOM stores the inspection report in connection with theobject and removes the inspection from the task listing. Step 590 isfollowed by step 595, in the JOM schedules the inspection to be reviewedby the jurisdiction. The JOM generates and places a task in thejurisdiction task listing. The jurisdiction review routine process isdescribed in further detail in reference to FIG. 6.

Step 595 is followed by step 597, in which the JOM determines if theobject is to be decommissioned. If the object is to decommissioned theYES branch of step 597 is followed to step 597, in which the JOM removesthe association of current objects located at that location. Step 597 isfollowed by step 505, in which the process is repeated. If the object isto decommissioned the YES branch of step 597 is followed to step 597, inwhich the inspection process is repeated.

FIG. 6 illustrates a review routine process. The initial step of theroutine is step 605, in which the JOM determines if the user desires toperform a review. A jurisdictional reviewer has a hot link to reviews onthe user's homepage. If the reviewer has not activated a review request,the NO branch of step 605 is followed and the review routine iscompleted. If the user desires to perform a review, the YES branch ofstep 605 is followed to step 610.

In step 610, the JOM determines if the user has the permission settingto perform reviews for the jurisdiction. The user permissions isdescribed in greater detail in reference to the administration unit ofFIG. 4. If the user does not have the requisite permission to performreviews for that jurisdiction, the NO branch of step 610 is followed tostep 605, in which the JOM determines if the user desires to perform areview. If the user has the requisite permission to perform reviews forthat jurisdiction, the YES branch of step 610 is followed to step 615,in which the JOM determines which review is to be performed. Followingthe review hot link, the user can select the review desired.

In step 615, the JOM determines the review the user desires to perform.If the user has not selected a particular review, the NO branch of step615 is followed to step 615, in which the JOM awaits the selection. Uponselection, the YES branch of 615 is followed to step 620.

In step 620, the JOM display the inspection information for review bythe jurisdiction. Step 620 is followed by step 630, in which the JOMreceives the review input via interaction with the reviewer's webbrowser. Step 630 is followed by step 635, in which the JOM determinesif the reviewer has accepted the inspection. If the reviewer has notaccepted the inspection, the NO branch of step 635 is followed to step665, in which the JOM determines if the user has rejected the inspected.If the reviewer has accepted the inspection, the YES branch of step 635is followed to step 640.

In step 640, the JOM stores the review comments along with the reviewdate and the name of the reviewer in association with the inspection andremoves the inspection from the task listing. Step 640 is followed bystep 645, in which the JOM performs notification of the acceptance andprompts payment. Notification can be performed by email or simplyupdating the accounting unit to reflect that the payment is due.

Step 645 is followed by step 650, in which the JOM determines if theowner has paid the requisite fees. Fee payment is described in greaterdetail in the accounting unit in reference to FIG. 4. If the fees havenot been paid, the NO branch of 650 is followed to step 650, in whichthe JOM awaits payment. If the fee payment has been received, the YESbranch of 650 is followed to step 655, in which the JOM directs the feeto be applied to this object. Step 655 is followed by step 660, in whichthe JOM authorizes provision of the certificate. Upon authorization, theowner can requisite a printing of the certificate.

Step 660 is followed by step 662, in which the JOM updates theinspection date. The updated inspection date is used by the JOM tocalculate the next required inspection. Step 662 is followed to step605, in which the review process is repeated.

In step 665, the JOM determines if the reviewer has rejected theinspection. If the reviewer has not rejected the inspection, the NObranch of step 665 is followed to step 690. If the reviewer has rejectedthe inspection, the YES branch of step 665 is followed to step 670.

In step 670, the inspection is removed from the task listing. Step 670is followed by step 675, in which notification of the rejectedinspection is performed. Notification can be by email or by simplyupdating the inspection records associated with the object.

Step 675 is followed by step 680, in which the remedial action tocorrect the rejection is entered into the JOM. Step 680 is followed bystep 680, in which a review is scheduled for the repair. The JOMgenerates a task for another review to be performed by the jurisdiction.Step 685 is followed to step 605, in which the JOM determines if areview is to be performed.

In step 690, the JOM determines whether the reviewer has cancelled thereview. If the reviewer has not cancelled the review, the NO branch ofstep 690 is followed to step 635 in which the JOM determines awaits adetermination by the reviewer of the inspection report. If the reviewerhas cancelled the review, the YES branch of step 690 is followed to step605, in which the JOM repeats the review process.

FIG. 7 illustrates a data file structure of information stored in theJOM database 350. The information illustrated in FIG. 7 is organizedlogically in conventional data files in the known manner, associatedwith one or more owners of pressure vessels or boilers.

In accordance with the illustrated embodiment, the JOM storesinformation associated with a plurality of different owners, e.g. OWNER1 710, OWNER 2 712, through OWNER N 714. Object owners are associatedwith locations, e.g. LOCATION 1 720, LOCATION 2 722, through LOCATION N724. Likewise, locations may be associated with a plurality of objectsoperated at each location, e.g. BOILER 1 740, PRESSURE VESSEL 2 742,through BOILER N 744. Each object is associated with correspondinginsurance information that identifies the insurer and the company thatperforms the object inspections, e.g. INSURANCE 750. In addition, theobjects are associated with their required inspections 760, e.g.INSPECTION 1 760 INSPECTION 2 762 through INSPECTION N 764. Eachinspection is associated with an inspector, e.g. INSPECTOR790 and areview, e.g. REVIEW 780. Information stored in the database 350 can beretrieved for data manipulation and reporting.

In accordance with one disclosed embodiment, owner has certaininformation associated with it. Illustrated is information stored inconnection with a file for OWNER 1 710. Such information includes thecompany profile. Profile information identifies the company such as bymailing address, nature of the business, and general contact points.Each owner designates the employees, or users, that can authorizecertain transactions. The authority level along with a user name andassociated password or other security information is stored as userdata. The JOM assigns each owner a unique identifier number. Inaddition, each owner has one or more associated locations.

The location files as illustrated in the LOCATION 1 file 720 storeslocation information. This information includes the physical address,county, contact information, billing address, and company information.The JOM assigns each location a unique identifier referred to as alocation number. In addition the location file 720 stores the SIC(standard industry code) associated with the use of the object. Also,the population density is stored because some regulations may depend onthe population density of the area in which the object is used. Eachlocation has associated with it object files, e.g. BOILER 1 740,PRESSURE VESSEL 2 742, BOILER 3 744, for the objects used at thelocation.

The object file, BOILER 1 740, illustrates the stored detailedinformation about the object. Each object is identified by itsjurisdiction assigned identifier and a separate other identifier such asthe manufacturer's number. The object information includes the assignedowner identification; the location of the object, year installed, and ifinstalled new, the year built, capacity of the object, and its currentstatus. If an object is insured, the insurance information, INSURANCE750, is associated with the object. In addition, information of its useis stored. Additional use data includes the method of fire, energyinput, heating surface, and he1 type. Safety information is alsorecorded in conjunction with object. This safety information includessafety valve information, the maximum allowable working pressure (MAWP),and the low water cut-off(LWCO). If the object is moved and requires avariance, any approved variance by the jurisdiction is recorded. Eachobject is required to pass periodic inspections to ensure the object isin compliance with the jurisdiction's regulations. The inspection files,e.g. INSPECTION 1760, are associated with the object. Additionally, thepayment of the requisite fees must be current before a certificate canbe lo issued. Payment information is stored in associated payment files,e.g. PAYMENT 1730. In Addition, object repair information is associatedwith each object to provide a historical view of the object.

Insurance information is associated with the each object, as illustratedin INSURANCE 750 file. The insurance information includes the companyname, the policy information including the effective and end dates, andthe contact information. Any identifier utilized by the insurancecompany to uniquely distinguish the insured object is also recorded. Theinsurance company is responsible to provide the object inspections.

Object inspections and associated information are stored in theinspection files. INSPECTION 1760 illustrates the information stored inan inspection file. This information includes the inspection date,comments, violations and recommendations, and certificate information.Each inspection has associated with it an inspector and a jurisdictionreview.

The jurisdiction review file is illustrated by REVIEW 780. This fileincludes the reviewer, the review date, jurisdiction performing thereview, the result and associated comments.

The inspector file is illustrated by INSPECTOR 790. This file includesthe inspector's name, contact information, commission number, theassociated jurisdiction for the commission, and the commission's startand end dates.

Issuance of a certificate requires the payment of the requisite fees.The payment information is stored in the payment files, e.g. PAYMENT1730. The payment file stores the check or credit card information, thedata entry date, the account identifier, and payment amount. Inaddition, overpayments can be allocated to the payment for a differentobject.

The data stored in the database is not overwritten upon the storage ofedit information. The new information is appended to the existinginformation. A review typically displays the old information as well asthe new information to allow the reviewer to easily identify thechanges. In most other situation, the JOM display only the latestrevised information.

FIG. 8 illustrates a flow chart of an embodiment of one user interfaceprocess. The process starts at step 805, in which the user requests anaccess web page provided by the JOM.

The JOM prompts the user for the username and password. Step 810 followsstep 805, in which the JOM determines if the user is authorized to thesystem. If the user is not authorized, access is denied and the NObranch of step 810 is followed to step 805, in which the user mayattempt a valid login. If the user is authorized, the JOM provides theuser with a homepage generated for that user and the YES branch of step810 is followed to step 815.

In step 815, the JOM determines if the user has requested to access theaccounting unit. A more detailed description of the accounting unit isprovided in reference to FIG. 4. If the user has not requested theaccounting unit or is denied access, the NO branch of step 815 isfollowed to step 825, in which the JOM determines if the user desires toaccess the work assignment unit. If the user has requested theaccounting unit and has the requisite permission, the YES branch of step815 is followed to routine 820, in which the JOM provides access thework assignment unit. Routine 820 is described in greater detail inreference to FIG. 9. Routine 820 is followed by step 825.

In step 825, the JOM determines if the user has requested to access thework assignment unit. A more detailed description of the work assignmentunit is provided in reference to FIG. 4. If the user has not requestedthe work assignment unit or is denied access, the NO branch of step 825is followed to step 835, in which the JOM determines if the user desiresto access the administration unit. If the user has requested the workassignment unit and has the requisite permission, the YES branch of step825 is followed to routine 830, in which the JOM provides access thework assignment unit. Routine 830 is described in greater detail inreference to FIG. 10. Routine 830 is followed by step 835.

In step 835, the JOM determines if the user has requested to access theadministration unit. A more detailed description of the administrationunit is provided in reference to FIG. 4. If the user has not requestedthe administration unit or is denied access, the NO branch of step 835is followed to step 845, in which the JOM determines if the user desiresto access the location unit. If the user has requested theadministration unit and has the requisite permission, the YES branch ofstep 835 is followed to routine 840, in which the JOM provides accessthe administration unit. Routine 840 is described in greater detail inreference to FIG. 11. Routine 840 is followed by step 845.

In step 845, the JOM determines if the user has requested to access thelocation unit. A more detailed description of the location unit isprovided in reference to FIG. 4, If the user has not requested thelocation unit or is denied access, the NO branch of step 845 is followedto step 855, in which the JOM determines if the user desires to accessthe object unit. If the user has requested the location unit and has therequisite permission, the YES branch of step 845 is followed to routine850, in which the JOM provides access the location unit. Routine 850 isdescribed in greater detail in reference to FIG. 12. Routine 850 isfollowed by step 855.

In step 855, the JOM determines if the user has requested to access theobject unit. A more detailed description of the object unit is providedin reference to FIG. 4. If the user has not requested the object unit oris denied access, the NO branch of step 855 is followed to step 865, inwhich the JOM determines if the user desires to access the inspectionunit. If the user has requested the object unit and has the requisitepermission, the YES branch of step 855 is followed to routine 860, inwhich the JOM provides access the object unit. Routine 860 is describedin greater detail in reference to FIG. 13. Routine 860 is followed bystep 865.

In step 865, the JOM determines if the user has requested to access theinspection unit. A more detailed description of the inspection unit isprovided in reference to FIG. 4. If the user has not requested theinspection unit or is denied access, the NO branch of step 865 isfollowed to step 875, in which the JOM determines if the user desires toaccess the review unit. If the user has requested the inspection unitand has the requisite permission, the YES branch of step 865 is followedto routine 870, in which the JOM provides access the object unit.Routine 870 is described in greater detail in reference to FIG. 14.Routine 870 is followed by step 875.

In step 875, the JOM determines if the user has requested to access thereview unit. A more detailed description of the review unit is providedin reference to FIG. 4. If the user has not requested the review unit oris denied access, the NO branch of step 875 is followed to step 885, inwhich the JOM determines if the user desires to log out. If the user hasrequested the review unit and has the requisite permission, the YESbranch of step 875 is followed to step 880, in which the JOM providesaccess the review unit. Routine 880 is described in greater detail inreference to FIG. 15. Routine 880 is followed by step 885.

In step 885, the JOM determines if the user desires to log out. If theuser has not activated a log out button, the NO branch of step 885 isfollowed to step 815, in which the JOM awaits a determination by theuser. If the user has decided to log out, the NO branch of step 885 isfollowed and the user interface routine is completed.

FIG. 9 illustrates an embodiment of an accounting interface routine 820.The routine 820 is accessed upon a user requesting accounting functionsfrom step 815 of FIG. 8. The routine begins at step 902, in which theJOM determines if the user desires to add payment. If paymentinformation is not to be added, the NO branch of step 902 is followed tostep 910, in which the JOM determines if a payment is to be edited. Ifpayment information is to be entered, the YES branch of step 902 isfollowed to step 904.

In step 904, the JOM accepts payment information. Payment informationcan include automatic bank withdrawal information, draft withdrawalinformation, or credit card information. Step 904 is followed by step906, in which the user selects the objects to which the payment applies.Step 906 is followed by step 908, in which the user selects to submitthe payment information. If the user decides not to submit the paymentinformation, the NO branch of step 908 is followed to step 902, in theuser determines if payment information is to be entered. If the paymentinformation is submitted, the YES branch of step 908 is followed to step910.

In step 910, the JOM determines if payment is to be edited. If paymentinformation is not to be edited, the NO branch of step 910 is followedto step 930, in which the JOM determines if a payment is to beprocessed. If a payment is to be edited, the YES branch of step 910 isfollowed to step 912, in which the JOM determines if the user desires tochange payment information. If payment information is not be changed,the NO branch of step 912 is followed to step 924, in which the JOMdetermines if a payment is to be deleted. If payment information is tobe changed, the YES branch of step 912 is followed to step 914, in whichthe JOM displays and accepts edit payment information.

Step 914 is followed by step 918, in which the user can change theobjects to which any payments are to be applied. Step 918 is followed bystep 920, in which the JOM determines if the payment edit is to besubmitted. If the payment edit is not to be submitted the NO branch ofstep 920 is followed to step 912, in which the JOM determines if theuser desires to change payment information. If the payment informationis to be submitted, the YES branch of step 920 is followed to step 924,in which the JOM determines is the payment, is to be deleted. If thepayment is not to be deleted, the NO branch of step 924 is followed tostep 930, in which the JOM determines if the user desires to process apayment. If a payment is to be voided, the YES branch of step 924 isfollowed to step 926, in which the user designates the payment todelete. Step 926 is followed by step 928, in which the JOM determines ifthe user submits the delete payment request. If the delete request isnot submitted, the NO branch of step 928 is followed to step 924, inwhich the JOM determines if the user desires to delete a payment. If theuser selects to submit a deletion, the YES branch of step 928 isfollowed to step 930.

In step 930, the JOM determines if the desires to process a payment. Ifthe user does not desire to process a payment, the NO branch of step 930is followed to step 936, in which the JOM determines if the user desiresan invoice search. If the user desires to process a payment, the YESbranch of step 930 is followed to step 932. In step 932, the JOMprovides an accounting of the payment received and a listing of objectswith their associated fees. The JOM enables the users to select theobjects for which to apply payments and provides an accounting of moniesleft after payment. Step 932 is followed to step 934, in which the userselects to submit the applied payment. If the user does not select tosubmit the application, the NO branch of step 934 is followed to step930, in which the user determines if payments are to be applied to anobject. If the users select to submit the payment application, the YESbranch of step 934 is followed to step 936 and the accountinginformation is updated.

In step 936, the JOM determines if the user desires an invoice search.If an invoice search is not to be performed, the NO branch of step 936is followed to step 950, in which the JOM determines whether to print acertificate. If an invoice search is to be performed, the YES branch ofstep 936 is followed to step 938, in which the user enters the searchcriteria. Step 938 is followed by step 940, in which the JOM determineswhether the search criterion is submitted. If the criterion is not to besubmitted, the NO branch of step 940 is followed to step 936, in whichthe JOM determines whether an invoice search is to be performed. If thesearch criterion is submitted, the yes branch of step 940 is followed tostep 942 and the search is performed with the results displayed.

In step 942, the JOM determines whether to print the invoice. If theinvoice is not to be printed, the NO branch of step 942 is followed tostep 950, in which the JOM determines whether to print a certificate. Ifthe invoice is to be printed, the YES branch of step 942 is followed tostep 944.

In step 944, the JOM accepts the user selection of the invoicesdisplayed as a result of the submission of the invoice search. Step 944is followed by step 946, in which the print option for the invoice isdetermined. Step 946 is followed by step 948, in which the JOMdetermines whether the print request is submitted. If the print requestis not to be submitted, the NO branch of step 948 is followed to step942, in which the JOM determines if an invoice is to be printed. If theprint request is submitted, the YES branch of step 948 is followed tostep 950.

In step 950, the JOM determines whether to print a certificate. If acertificate is not to be printed, the NO branch of step 950 is followedand the routine is returned to perform step 825 of FIG. 8. If acertificate is to be printed, the YES branch of step 950 is followed tostep 952, in which the JOM determines if an open violation occurs forthe object. If a lo violation is open, the YES branch of step 952 isfollowed to step and no certificate is printed. If an open violationdoes not exist, the NO branch of step 952 is followed to step 954. Ifstep 954, if a hold status has been placed on the object, no certificatecan be printed and YES branch is followed to step 950. If a hold statusis not current, the NO branch of step 954 is followed to step 956, inwhich the JOM determines if fees are due. If the fees have not beenpaid, the Yes branch of step 956 is followed and the certificate cannotbe printed. If the requisite fees have been paid, the NO branch of 956is followed to step 958, in which the JOM generates and prints acertificate. After step 958, the routine is returned to perform step 825of FIG. 8.

FIG. 10 illustrates an inspection assignment routine 830. The routine830 is accessed upon a user requesting assignment functions from step825 of FIG. 8. The routine begins with step 1002, in which the JOMdetermines whether to display the work schedule. If the schedule is notto be displayed, the NO branch of step 1002 is followed to step 1006, inwhich the JOM determines whether new work assignments are to be added.If the schedule is to be viewed, the YES branch of step 1002 is followedto step 1004, in which the JOM displays the current scheduledinspections. Step 1004 is followed by step 1006.

In step 1006, the JOM determines if new assignments are to be added tothe work assignment. If new work assignments are not to be scheduled,the NO branch of step 1006 is followed to step 1016, in which the JOMdetermines whether assignments are to be edited. If new assignments areto be scheduled, the YES branch of step 1006 is followed to step 1008.In step 1008, the current locations requiring inspections are displayed.Step 1008 is followed by step 1010, in which the JOM determines if theuser has selected a location to inspect. If a location is not to beselected, the NO branch of step 1010 is followed to step 1006, in whichthe user determines whether to add an assignment. If a location isselected, the YES branch of step 1010 is followed to step 1012.

In step 1012, an inspection is slated to be performed. Step 1012 isfollowed by step 1014, in the user submits the added scheduledinspection. If the inspection is not to be scheduled, the NO branch ofstep 1014 is followed to 1006, in which the user determines whether toadd an assignment. If the inspection is to be scheduled, the YES branchof step 1014 is followed to step 1016.

In step 1016, the JOM determines whether the schedule is to be edited.If not assignment edit is to be performed, the NO branch of step 1016 isfollowed and the routine is lo returned to perform step 835 of FIG. 8.If an assignment is to be edited, the YES branch of step 1016 isfollowed to step 1018.

In step 1018, the current schedule is edited by the user. Step 1018 isfollowed by step 1020, in which the JOM determines if the edit is to besubmitted. If the edit is submitted, the YES branch of step 1020 isfollowed to perform step 835 of FIG. 8. If the edit is not submitted,the NO branch of step 1020 is followed to step 1022, in which the JOMdetermines whether an assignment is to be deleted. If no assignment isto be deleted, the NO branch of step 1022 is followed to perform step835 of FIG. 8. If an assignment is to be deleted, the YES branch of step1022 is followed to step 1024.

In step 1024, the user selects the assignments that are to be deletedfrom the work schedule. Step 1024 is followed by step 1026, in which theJOM determines if the selected assignments are submitted for deletion.If the assignments are not to be deleted, the NO branch of step 1026 isfollowed to step 1022, in which the user determines whether to delete anassignment. If the deletion is submitted, the YES branch of step 1026 isfollowed to step 1028. In step 1028, the assignment is deleted from theinspectors work schedule. Step 1028 is followed to return the routine toperform step 835 of FIG. 8.

FIG. 11 illustrates an embodiment of an administration routine 840. Theroutine 840 is accessed upon a user requesting administration functionsfrom step 835 of FIG. 8. The routine 840 begins with step 1102, in whichthe JOM determines whether to administer a system message. If a systemmessage is not to be affected, the NO branch of step 1102 is followed tostep 1112, in which the IOM determines whether to administer a safetybulletin. If a system message is to be affected, the YES branch of step1102 is followed to step 1104. In step 1104, the JOM determines if themessage is to be added, edited, or deleted. If a message is not to beaffected, the NO branch of step 1104 is followed to step 1102, in whichthe JOM determines whether a system message is to be administered. If asystem message is to be affected, the YES branch of step 1104 isfollowed to step 1106.

In step 1106, a search is performed, if necessary, to find systemmessage to be altered. Step 1106 is followed by step 1108, in which thesystem message is altered. Step 1108 is followed by step 1110, in whichthe JOM determines if the affected message is submitted. If thealteration is not submitted, the NO branch of step 1110 is followed tostep 1102, in which the JOM determines if a system message is to bealtered. If the alteration is submitted, the alteration is recorded andthe YES branch of step 1110 is followed to step 1112.

In step 1112, the JOM determines whether to administer a safetybulletin. If a safety bulletin is not to be affected, the NO branch ofstep 1112 is followed to step 1122, in which the JOM determines whetherto administer user data. If a safety bulletin is to be affected, the YESbranch of step 1112 is followed to step 1114. In step 1114, the JOMdetermines if the bulletin is to be added, edited, or deleted. If abulletin is not to be affected, the NO branch of step 1114 is followedto step 1112, in which the JOM determines whether a safety bulletin isto be administered. If a safety bulletin is to be affected, the YESbranch of step 1114 is followed to step 1116.

In step 1116, a search is performed, if necessary, to find the safetybulletin to be altered. Step 1116 is followed by step 1118, in which thebulletin is altered. Step 1118 is followed by step 1120, in which theJOM determines if the affected bulletin is submitted. If the alterationis not submitted, the NO branch of step 1120 is followed to step 1112,in which the JOM determines if a safety bulletin is to be altered. Ifthe alteration is submitted, the alteration is recorded and the YESbranch of step 1120 is followed to step 1122.

In step 1122, the JOM determines whether to administer user data. Ifuser data is not to be affected, the NO branch of step 1122 is followedto step 1132, in which the JOM determines whether to administer grouppermissions. If user data is to be affected, the YES branch of step 1122is followed to step 1124. In step 1124, the JOM determines if the userdata is to be added, edited, or deleted. If a user is not to beaffected, the NO branch of step 1124 is followed to step 1122, in whichthe JOM determines whether user data is to be administered. If a user isto be affected, the YES branch of step 1124 is followed to step 1126.

In step 1126, a search is performed, if necessary, to find the user datato be altered. Step 1126 is followed by step 1128, in which the userdata is altered. Step 1128 is followed by step 1130, in which the JOMdetermines if the user data is to be submitted. If the user data is notsubmitted, the NO branch of step 1130 is followed to step 1122, in whichthe JOM determines if user data is to be altered. If the alteration issubmitted, the alteration is recorded the YES branch of step 1130 isfollowed to step 1132.

In step 1132, the JOM determines whether to administer grouppermissions. If group permission is not to be affected, the NO branch ofstep 1132 is followed to step 1142, in which the JOM determines whetherto administer user commissions. If group permission is to be affected,the YES branch of step 1132 is followed to step 1134. In step 1134, theJOM determines if the group permission is to be added, edited, ordeleted. If group permission is not to be affected, the NO branch ofstep 1134 is followed to step 1132, in which the JOM determines whethergroup permission is to be administered. If group permission is to beaffected, the YES branch of step 1134 is followed to step 1136.

In step 1136, a search is performed, if necessary, to find the user tobe altered. Step 1136 is followed by step 1138, in which the grouppermission is altered. Step 1138 is followed by step 1140, in which theJOM determines if the group permission is to be submitted. If the grouppermission is not submitted, the NO branch of step 1140 is followed tostep 1132, in which the JOM determines if group permission is to bealtered. If the alteration is submitted, the alteration is recorded theYES branch of step 1140 is followed to step 1142.

In step 1142, the JOM determines whether to administer commissions. If acommission is not to be affected, the NO branch of step 1142 is followedto step 1144, in which the JOM determines whether to administer usercommissions. If a commission is to be affected, the YES branch of step1142 is followed to step 1144. In step 1144, the JOM determines if acommission is to be added, edited, or deleted. If a commission is not tobe affected, the NO branch of step 1144 is followed to step 1142, inwhich the JOM determines whether a commission is to be administered. Ifa commission is to be affected, the YES branch of step 1144 is followedto step 1146.

In step 1146, a search is performed, if necessary, to find the user tobe altered. Step 1146 is followed by step 1148, in which a commission isaltered. Step 1148 is followed by step 1150, in which the JOM determinesif a commission is to be submitted. If a commission is not submitted,the NO branch of step 1150 is followed to step 1142, in which the JOMdetermines if a commission is to be altered. If the alteration issubmitted, the alteration is recorded the YES branch of step 1150 isfollowed to step 1152.

In step 1152, the JOM determines whether to administer an insurancepolicy. If an insurance policy is not to be affected, the NO branch ofstep 1152 is followed to step 1162, in which the JOM determines whetherto administer a report. If an insurance policy is to be affected, theYES branch of step 1152 is followed to step 1154. In step 1154, the JOMdetermines if an insurance policy is to be added, edited, or deleted. Ifan insurance policy is not to be affected, the NO branch of step 1154 isfollowed to step 1152, in which the JOM determines whether an insurancepolicy is to be administered. If an insurance policy is to be affected,the YES branch of step 1154 is followed to step 1156.

In step 1156, a search is performed, if necessary, to find the object tobe altered. Step 1156 is followed by step 1158, in which an insurancepolicy is altered. Step 1158 is followed by step 1160, in which the JOMdetermines if an insurance policy is to be submitted. If an insurancepolicy is not submitted, the NO branch of step 1160 is followed to step1152, in which the JOM determines if an insurance policy is to bealtered. If the alteration is submitted, the alteration is recorded theYES branch of step 1160 is followed to step 1162.

In step 1162, the JOM determines whether to display reports. If a reportis not to be displayed, the NO branch of step 1162 is followed and theroutine is returned to perform step 845 of FIG. 8. If a report is to beviewed, the YES branch of step 1162 is followed to step 1164. In step1164, the viewer selects the report type to be viewed. Step 1164 isfollowed by step 1666, in which the JOM displays the requested reports.Step 1166 is followed by step 1168, in the JOM determines whether toexit the report display. If the report display is not exited, the NObranch of step 168 is followed to step 166 and the selected reports arecontinued to be displayed. If the user requests to exit the reportdisplay, the YES branch of step 1168 is followed and routine is returnedto perform step 845 of FIG. 8.

FIG. 12 illustrates an embodiment of a location interface routine 850.The routine 850 is accessed upon a user requesting location functionsfrom step 845 of FIG. 8. Routine 850 begins with step 1202, in which theJOM determines whether a location search is to be performed. If alocation search is not to be performed, the NO branch of step 1202 isfollowed by step 1228, in which the JOM determines if the user is addinga location. If a location search is to be performed, the YES branch ofstep 1202 is followed to step 2204.

In step 1204, the JOM accepts the search criteria inputted by the user.Step 1204 is followed by step 1206, in which the JOM performs the searchand display the results. Step 1206 is followed by step 1208, in whichthe JOM determines if a location is to be selected. If a location is notto be selected, the NO branch of step 1208 is followed to step 1202, inwhich the JOM determines whether to perform a location search. If aLocation is selected, the YES branch of step 1208 is followed to step1210.

In step 1210, the JOM determines if a location edit is to be performed.If location data is not to be edited, the NO branch of step 1210 isfollowed to step 1216, in which the JOM determines if past inspectionsare to be accessed. If a location edit is to be performed, the YESbranch of step 1210 is followed to 1212. In step 1212, the JOM acceptsupdated location information.

Step 1212 is followed by step 1214, in which the JOM determines if theedited lo location data is to be submitted. If the location edit is notto be submitted, the NO branch of step 1214 is followed to step 1210, inwhich a determination is made whether to edit location information. Ifthe location edit is submitted, the JOM stores the update and the YESbranch of step 1214 is followed to step 1216.

In step 1216, a determination of whether to access past inspections. Ifpast inspections are not to be accessed, the NO branch of step 1216 isfollowed to step 1220, in which the JOM determines if pendinginspections are to be accessed. If past inspections are to be accessed,the YES branch of step 1216 is followed to step 1218.

In step 1218, recent inspections are displayed for access by the user.User interaction with inspection functions is described in greaterdetail in reference to FIG. 14. Step 1218 is followed by step 1220, inwhich a determination is made whether to access pending inspections.

In step 1220, a determination of whether to access pending inspections.If pending inspection are not to be performed, the NO branch of step1220 is followed to step 1224, in which the JOM determines if an objectis to be selected. If pending inspections are to be accessed, the YESbranch of step 1220 is followed to step 1222. In step 1222, pendinginspections are displayed for access by the user. User interaction withassignment functions is described in greater detail in reference to FIG.10. Step 1222 is followed by step 1224.

In step 1224, a determination is made whether to access objectfunctions. If object functions are not to be accessed, the NO branch ofstep 1224 is followed by step 1228, in which the JOM determines whethera new location information is to be added. If object functions are to beaccessed, the YES branch of step 1224 is followed by step 1226, in whichthe location objects are displayed for further interaction. Interactionwith objects is described in greater detail in reference to FIG. 13.Step 1226 is followed by step 1228.

In step 1228, the JOM decides whether to add a location. If a newlocation is not to be added, the NO branch is followed and the routine850 is returned to perform step 855 of FIG. 8. If a new location is tobe added, the YES branch of step 1228 is followed to step 1230. In step1230, new location data is inputted by the user. Step 1230 is followedby step 1232, in which a determination is made whether to submit the newlocation data. If the new location data is not to be submitted, the NObranch of step 1232 is followed to step 1228, in which a determinationis made whether to add a new location. If new location data is to besubmitted, the YES branch of step 1232 is followed and the routine 850is returned to perform step 855 of FIG. 8.

FIG. 13 illustrates an embodiment of a object interface routine 860. Theroutine 860 is accessed upon a user requesting object functions fromstep 855 of FIG. 8. Routine 860 begins with step 1302, in which the JOMdetermines whether a location search is to be performed. If a locationsearch is not to be performed, the NO branch of step 1302 is followed tostep 1302, in which the JOM determines if location search is to beperformed. If a location search is to be performed, the YES branch ofstep 1302 is followed to step 1304.

In step 1304, the location search screen is displayed and the criterionis entered. Step 1304 is followed by step 1306 the location search isperformed. Step 1306 is followed by step 1308, in which the location ofthe object is selected. Step 1308 is followed by step 1310, in which adetermination is made whether to add an object. If an object is not tobe added the NO branch of step 1310 is followed by step 1316, in which adetermination is made whether to edit object information. If an objectis to added, the YES branch of step 1310 is followed to step 1312.

In step 1312, the new object information is inputted by the user. Step1312 is followed by step 1314, in which a determination is made whetherto submit the new information. If the addition is not to be submitted,the NO branch of step 1314 is followed to step 1310, in which adetermination is made whether to add an object. If the new objectinformation is to be submitted, the YES branch of step 1314 is followedto step 1316.

In step 1316, a determination is made whether object information is tobe edited. If an object is not to be edited, the NO branch of step 1316is followed to 1322, in which a determination is made whether to displayobject history. If object information is to edited the YES branch ofstep 1316 is followed to step 1318, in which the object data is edited.Step 1318 is followed by step 1320, in which a determination is madewhether to submitted the edit. If the edit is not to be submitted, theNO branch of step 1320 is followed to step 1316, in which adetermination is made whether to edit an object. If the object edit isto be submitted, the Yes branch of step 1320 is followed to step 1322.

In step 1322, a determination is made whether to access the objecthistory. If the object history is not to be displayed, the NO branch ofstep 1322 is followed to step 1336, in which a determination is madewhether to update object information caused by the movement of theobject's location. If the object has not been moved, the NO branch ofstep 1336 is followed and routine 860 is returned to perform step 865 ofFIG. 8. If the object has been moved, the YES branch of step 1336 isfollowed to step 1338, in which the new location information isinputted. Step 1338 is followed by step 1340, in which the contactinformation for the new location is entered. Step 1340 is followed bystep 1342.

In step 1342, a determination is made whether to enter variationinformation. If a variation is not required, the NO branch of step 1342is followed and the routine 860 is returned to perform step 865 of FIG.8. If variation information is to be entered, the YES branch of step1342 is followed to step 1344. In step 1344, the variations approved bythe is jurisdiction are entered. After step 1344, the routine 860 isreturned to perform step 865 of FIG. 8.

FIG. 14 illustrates an embodiment of a inspection interface routine 870.The routine 870 is accessed upon a user requesting location functionsfrom step 845 of FIG. 8. Routine 850 begins with step 1202, in which theJOM determines that a location search is to be performed. Step 1402 isfollowed by step 1404, in which the location search criteria is entered.Step 1404 is followed by step 1406, in which the search is performed andthe results are displayed. Step 1406, is followed by step 1408, in whichthe desired location is selected.

Step 1408 is followed by step 1410, in which a determination is madewhether to access the edit location functions. If edit locationfunctions are not to be accessed, the NO branch of step 1410 is followedand the routine 870 is returned to perform step 875 of FIG. 8. If editlocation functions are to be entered, the YES branch of step 1410 isfollowed to step 1412, in which a determination is made whether to entera new inspection information.

If new inspection information is not to be entered, the NO branch ofstep 1412 is followed to step 1420, in which the object functions areaccessed. If new inspection information is to be entered, the YES branchof step 1412 is followed to step 1414. In step 1414, the user selectsthe appropriate object at that location. Step 1414 is followed by step1416, the inspection entry screen is displayed and the inspection datais entered. Step 1416 is followed by step 1418, in which a determinationis made to submit the inspection. If the inspection is not to besubmitted, the NO branch of step 1418 is followed to step 1412, in whicha determination is made whether to enter a new inspection. If the newinspection information is submitted, the YES branch of step 141 8 isfollowed to step 1420.

In step 1420, the JOM determines if the object functions are to beaccessed. If the object functions are not to be accessed, the NO branchof step 1420 is followed and the routine 870 is returned to perform step875 of FIG. 8. If the object functions are to be accessed, the YESbranch of step 1420 is followed by step 1422, in which the user selectsthe appropriate object.

Step 1422 is followed by step 1424, in which a determination is madewhether to edit an inspection. If an inspection is not to be edited, theNO branch of step 1424 is followed to step 1430, in which adetermination is made whether to add or edit a repair information. If aninspection is to be edited, the YES branch of step 1424 is followed tostep 1426, in which the inspection information is entered.

Step 1426 is followed by step 1428, in which a determination is madewhether to submit the edit. If the edit is not to be submitted, the NObranch of step 1428 is followed to step 1424, in which a determinationis made whether to edit an inspection. If the edit is to submitted, theYES branch of step 1428 is followed to step 1430.

In step 1430, a determination is made whether to add or edit repairinformation. If repair information is not to be updated, the NO branchof step 1430 is followed to step 1436, in which a determination is madewhether to access inspection reports. If repair information is to beupdated, the YES branch of step 1430 is followed to step 1432, in whichthe repair information is entered.

Step 1432 is followed by step 1434, in which a determination is madewhether to submit the update. If the update is not to be submitted, theNO branch of step 1434 is followed to step 1430, in which adetermination is made whether to update repair information. If theupdate is to submitted, the YES branch of step 1434 is followed to step1436.

In step 1436, a determination is made whether to access inspectionreports. If inspection reports are not to be accessed, the NO branch ofstep 1436 is followed and the routine 870 is returned to perform step875 of FIG. 8. If reports are to be accessed, the YES branch of step1436 is followed to step 1438, in which the available reports are listedfor selection. After step 1438, the routine 870 is returned to performstep 875 of FIG. 8.

FIG. 15 illustrates an embodiment of a review interface routine 880. Theroutine 880 is accessed upon a user requesting review functions fromstep 875 of FIG. 8. Reviews to be performed for a jurisdiction arelisted in the task listing for that jurisdiction. Routine 880 beginswith step 1502, in which the JOM determines that a review is to beperformed.

If a review is not to be performed, the NO branch of step 1502 isfollowed and the routine 880 is returned to perform step 885 of FIG. 8.If a review is selected, the YES branch of step 1502 is followed to step1504. In step 1504, the JOM lists the items requiring review.Inspections, repairs, and some edits of object information requirejurisdictional reviews. Step 1504 is followed by step 1506.

In step 1506, a determination is made of the review item to be accessed.If no review item is to be accessed, the NO branch of step 1506 isfollowed to step 1502, in which a determination is made whether toperform a review. If a review is to be accessed, the reviewer selectsthe item and the YES branch of step 1506 is followed to step 1508.

In step 1508, the review information is displayed. The display lists thecurrent data and displays the old information for those items that havebeen edited. The display of the pervious information assists thereviewer with the performance of the review. Step 1508 is followed bystep 1510, in which the review performs the review and enters comments.

Step 1510 is followed by step 1512, in which a determination is madewhether to accept the inspection or update. If the item is accepted, theYES branch of 1512 is followed to step 1502, in which a determination ismade whether to perform another review. If the item is not accepted, theNO branch of 1512 is followed to step 1514, in which a determination ismade whether to reject the item.

If the item is not to be rejected, the NO branch of step 1514 isfollowed to step 1502, and a determination is made whether to perform areview. If the item is to be rejected, the YES branch of step 1514 isfollowed to step 1516. In step 1516, the review is complete and thereason for rejection is entered. Step 1516 is followed by step 1518, inwhich a determination is made whether to submit the rejection. If therejection is not to be submitted, the NO branch of step 1518 is followedto step 1514, in which a determination is made whether the item is to berejected. If the rejection is to be submitted, the YES branch of step1518 is followed to step 1502, in which determinations are made whetherperform another review.

FIG. 16 illustrates a screen shot of a homepage 1600 generated by theJOM. The homepage 1600 has hot links to the location unit 1602, accountunit 1604, assignment unit 1606, review unit 1608, and an admin unit1610. The functional units are described in greater detail in referenceto FIG. 4. The homepage 1600 has a task listing 1612 listing tasksneeded to be performed. An task marked with a circled exclamation point1618 signals a task that has overdue items. The task listing 1612 has areview changes hot link 1620 to the reviews needing to be performed. Inthe illustrated task listing 1612, the review changes task 1620 hasreviews that are overdue for being reviewed.

The task listing 1612 also has a schedule inspection hot link 1622. Thishot link 1622 would cause the generation and display of the scheduleinspection web page. The illustrated homepage 1612 also lists a safetybulletin 1624 on boilers for perusal. In addition, the task listing 1612has a new inspection reporting procedure posted for viewing. Posting ofsafety bulletins or other informational bulletins is accomplished by theadministration unit. The administration unit can be quickly accessed bythe admin hot link 1610.

The homepage 1600 also has a saved queries listing 1628. In theillustrated homepage 1600, an object search hotlink 1628 is listed for aselected location. This hotlink 1628 provides a quick link to thispreviously performed search. In addition, a message listing 1616provides access to system message and system status.

Additionally, the homepage 1600 has a listing of several quick links1630. A quick link to schedules 1632, reports 1634, printing ofworksheets 1636, inspection performance 1638, and clearance pastschedules. These quick links 1630 enable the user to directly generateand display the associated web pages.

FIG. 17 illustrates a screen shot of a location web page 1700. Thelocation web page 1700 has a location details button 1710. The locationdetails web page enables the user to enter location information.Location details stored in the JOM database is discussed in greaterdetail in reference to FIG. 7. In addition, the location web page 1700has a contact details button 1720. The contact details web page enablesthe user to enter contact information. Contact details stored in the JOMdatabase is discussed in greater detail in reference to FIG. 7.Additionally, the location web page 1700 has a button 1760 to accessprevious recommendations and violations at the location.

The location web page 1700 also has an object button 1740. Activatingthe object button 1740 causes the presentment of object display options1740. The illustrated display option 1740 is by object type. In thiscase, all objects are presented namely three firetube boilers. Eachobject has a button 1750 that upon activation will provide the objecthistory. Each history line has an associated button 1755 that links theuser to the associated web page to view or edit the item.

FIG. 18 illustrates a screen shot of an object web page 1800. The webpage 1800 provides an easy mechanism for the user to enter or editobject details 1810 by the operation of a web browser. The web page 1800displays the date of last inspection. The illustrated object details1810 is for a boiler.

Typical object details 1810 includes the jurisdiction number for theobject as well as another object number such as the one assigned by themanufacturer. Detail information 1810 such as the location within theplant, year installed, the manufacturer, the year built, lo use, andother general information is entered. Heating information such as thefuel type, method of fire, input, heating surface, and capacity arerequested as boiler information. In addition safety information isentered such as the number of safety valves, the capacity provided, themaximum allowable working pressure (MAWP), and installation of a lowwater cutoff (LWCO). Some of the input boxes have drop down button forselection such as the fuel type. The illustrated fuel type for thisillustrated boiler is gas.

The object web page 1800 has an inspection history button 1820 that willdisplay the inspection history of the object. In addition, a listing ofpast recommendation and violations is accessed by associated button1840. Additionally, object repairs can be accessed from the listing ofthe repairs for the object by the object repairs button 1830.

The entered information on the object web page can be saved byactivation of the submit button 1862. The reset button 1862 provides ablank page for entry. The cancel button 1864 returns the user to thelocation web page illustrated in FIG. 17. The delete button 1864 willcause the object not to be listed at the location.

FIG. 19 illustrates a screen shot of an inspection web page 1900. Theinspection web page 1900 allows an inspector to enter or edit inspectiondata. The inspection web page 1900 displays the basic object information1910 associated with the inspection. This object information typicallyis the object type, the jurisdiction number, the manufacturer, and theyear the object was built. The inspection web page 1900 has a pull downbox 1915 with a listing of the categories of problems. In theillustrated inspection web page 1900, the violation is that the capacityis too low for the safety valve. A date entry box 1915 is provided alongwith a pop up calendar to easy date selection. The inspection status box1925 indicates the current status of the problem such as open or closed.The inspector's name 1930 is automatically generated by the userinformation. The type field 1935 lists the problem type such as aviolation or recommendation. The condition comment field accepts textfor the description of the problem. Likewise, the requirement fieldaccepts text for a description of the jurisdiction's requirement.

The inspector can submit and store the completed inspection byactivation of the submit button 1950. The cancel button returns the userto the previous web page without storing any information. In addition,the delete button allows for the inspection to deleted, if the user hasthe permission.

FIG. 20 illustrates a screenshot of a review web page 2000. The reviewpage 2000 lists the open reviews needing performance. Column 2010provides links to perform the review. Column 2020 lists the date of thatthe action was performed. Column 2030 lists the type of review required.The review can be change of location or object information, as well asthe review of an inspection. A description column 2040 provides asummary of the review item. In addition column 2050 will list thesubmitter of review.

FIG. 21 illustrates a screen shot of a review object web page 2100. Theweb page is 2100 has a button 2110 to review object edit. In theillustrated screen shot, the object edit for review is a boiler. The webpage 2100 lists the current values in column 2140. The web page alsodisplays an old value column 2150 for those values that have changed.For example, the date of last inspection has been updated. The web pagealso has owner details button 2120 and a comment field 2130. Thereviewer can accept the update by activation of the accept button 2160or reject the update by activation of the reject button 2180. The resetbutton 2180 resets the screen.

In view of the foregoing, it will be appreciated that the inventionprovides for a jurisdiction online manager. It should be understood thatthe foregoing relates only to the exemplary embodiments of the presentinvention, and that numerous changes may be made therein withoutdeparting from the spirit and scope of the invention as defined by thefollowing claims. Accordingly, it is the claims set forth below, and notmerely the foregoing illustration, which are intended to define theexclusive rights of the invention.

1. A method for sharing information regarding an inspectable objectbetween a jurisdictional entity having jurisdiction over objects of thattype of objects and a nonjurisdictional entity, comprising the steps of:receiving object data for an inspectable object at a computer system viaa global computer network; storing the object data in a database coupledto the computer system; retrieving and displaying online inspectiontemplate information based upon compliance requirements of thejurisdictional entity for the inspectable object; receiving objectinspection result data relating to an object resulting from inspectionof the object by an inspection entity based upon the inspection templateinformation via the global computer network; storing the objectinspection result data in the database; providing object inspectionresult data on-line to the jurisdictional entity via the global computernetwork; receiving review result data with respect to object inspectionresult data on-line from a person associated with the jurisdictionalentity via the global computer network; storing the review result datain the database; and providing the review result data on-line to anonjurisdictional entity via the global computer network.
 2. The methodof claim 1, wherein the inspectable objects are selected from the groupcomprising: pressure vessels, boilers, elevators, and/or amusement parkrides.
 3. The method of claim 1, further comprising the step ofproviding historical information data for the inspectable object.
 4. Themethod of claim 1, further comprising the steps of: receiving inspectorcommission information; and verifying inspector commission status basedon the inspector commission information prior to receiving the objectinspection result data.
 5. The method of claim 1, further comprising thesteps of: verifying that an object is in compliance with requirements ofthe jurisdictional entity; and issuing a certificate of compliance ifthe object is in compliance with said requirements.
 6. The method ofclaim 1, further comprising the steps of: determining an inspectiondate; and scheduling an inspection by an inspection entity.
 7. Themethod of claim 1, further comprising the step of providing to thejurisdictional entity for review changes to inspection result dataderived from a prior object inspection.
 8. The method of claim 1,wherein the nonjurisdictional entity is selected from the groupcomprising an inspection entity, an insurance company, and/or the ownerof the inspectable object.
 9. The method of claim 1, wherein thejurisdictional entity is a governmental regulatory agency.
 10. Themethod of claim 1, wherein the method is carried out for plurality ofinspectable objects involving a plurality of jurisdictional entities.11. The method of claim 1, wherein the information regarding theinspectable object is shared between the jurisdictional entity and aplurality of nonjurisdictional entities.
 12. A method for managinginspections of inspectable objects by facilitating the inspection ofobjects and review and approval of data from object inspection by ajurisdictional entity having a regulatory authority over the inspectableobjects, comprising the steps of: receiving template information basedupon compliance requirements for an object promulgated by ajurisdictional entity at a computer system via a global computernetwork; dispatching an inspector for a particular inspectable object byan inspection entity; providing inspection result data online resultingfrom inspection of the particular object by the inspection entity basedupon the template information displayed via the global computer networkfor review by the jurisdictional entity; and accessing review resultdata from the jurisdictional entity online via the global computernetwork.
 13. The method of claim 12, wherein the inspectable objects areselected from the group: pressure vessels, boilers, elevators, andamusement park rides.
 14. The method of claim 12, further comprising thestep of accessing historical information data for the particular object.15. The method of claim 12, further comprising the steps of receivinginspector commission information.
 16. The method of claim 12, furthercomprising the steps of: receiving an inspection notification; andscheduling an inspection date by the inspection entity.
 17. The methodof claim 12, further comprising the step of providing to thejurisdictional entity for review changes to inspection result dataderived from a prior object inspection.
 18. The method of claim 12,further comprising the step of: in response to receipt of approval ofobject inspection result data by a person associated with thejurisdictional entity, issuing a certificate of compliance relating tothe particular object.
 19. The method of claim 12, wherein theinspection entity is an insurance company.
 20. The method of claim 12,wherein the inspection entity is the owner of the inspectable object.21. The method of claim 12, wherein the step of accessing review resultdata from the jurisdictional entity online via the global computernetwork involves providing the information online to a plurality ofnonjurisdictional entities.
 22. A system for sharing informationregarding an inspectable object between a jurisdictional entity havingjurisdiction over objects of that type of objects and anonjurisdictional entity, comprising: a data network component forcoupling to a global communication network for communicating on-linewith a computer system of a jurisdictional entity and at least onenonjurisdictional entity; a server computer coupled to the data networkcomponent and operative for running application programs that containapplication program logic for: receiving and providing object dataonline relating to inspectable objects, displaying inspection templateinformation based upon compliance requirements of the jurisdictionalentity for use in entry of inspection data by an inspection entity,receiving and providing online inspection data resulting from inspectionof objects over which the jurisdictional entity has regulatoryauthority, and receiving and providing online inspection review dataresulting from review of inspection data with respect to objects; and adata storage system coupled to the at least one server computer forstoring application program data, object data, inspection data, andinspection review data.
 23. The system of claim 22, wherein the servercomputer further comprises application programming logic for providinghistorical information for the object.
 24. The system of claim 22,wherein the server computer further comprises application programminglogic for determining an inspection due date and for scheduling anobject inspection by the inspection entity.
 25. The system of claim 22,wherein the server computer further comprises application programminglogic for: providing an inspection result based on acceptance of objectinspection result data; receiving inspector commission data; andverifying inspector commission status based on the inspection commissiondata prior to providing the inspection result.
 26. The system of claim22, wherein the server computer further comprises applicationprogramming logic for receiving payment information.
 27. The system ofclaim 22, wherein the inspectable objects are selected from the group:pressure vessels, boilers, elevators, and amusement park rides.
 28. Thesystem of claim 22, wherein the server computer further comprisesapplication programming logic for providing to the jurisdictional entityfor review changes to inspection result data derived from a prior objectinspection.
 29. The system of claim 22, issuing a certificate ofcompliance relating to the particular object in response to receipt ofapproval of object inspection result data by a person associated withthe jurisdictional entity.
 30. The system of claim 22, wherein theinspection entity is an insurance company.
 31. The system of claim 22,wherein the inspection entity is the owner of the inspectable object.32. The system of claim 22, wherein server computer is operative inconnection with sharing information associated with a plurality ofinspectable objects involving a plurality of jurisdictional entities.33. The system of claim 22, wherein the server computer furthercomprises application programming logic for providing information fromthe system online to a plurality of nonjurisdictional entities.
 34. Amethod for managing inspections of inspectable objects by facilitatingthe inspection of objects and review and approval of data from objectinspection by a jurisdictional entity having a jurisdiction over theinspectable object, comprising the steps of: receiving object data foran inspectable object over which the jurisdictional entity has ajurisdiction; displaying inspection template information based uponcompliance requirements of the jurisdictional entity; receivinginspection result data relating to an object resulting from inspectionof the object by an inspection entity based upon the inspection templateinformation; providing inspection result data to the jurisdictionalentity for review and approval; providing to the jurisdictional entityfor review changes to inspection result data derived from a prior objectinspection by an inspection entity; receiving review result data withrespect to inspection result data from the jurisdictional entity; andproviding the review result data to the inspection entity.
 35. Themethod of claim 34, wherein the inspectable object is selected from thegroup: pressure vessels, boilers, elevators, and amusement park rides.36. The method of claim 34, further comprising the step of providinghistorical information data for the inspectable object.
 37. The methodof claim 34, further comprising the steps of: receiving inspectorcommission information; and verifying inspector commission status basedon the inspector commission information prior to receiving theinspection result data.
 38. The method of claim 34, further comprisingthe step of: in response to receipt of approval of inspection resultdata by a person associated with the jurisdictional entity, issuing acertificate of compliance relating to the particular object.
 39. Themethod of claim 34, further comprising the steps of: determining aninspection date; and scheduling an inspection by an inspection entity.40. The method of claim 34, further comprising the step of providing tothe jurisdictional entity for review changes to inspection result dataderived from a prior object inspection.
 41. The method of claim 34,further comprising the step of providing review result data to aninsurance company and/or the owner of the inspectable object.
 42. Themethod of claim 34, wherein the inspection entity is a governmentalinspection entity.
 43. The method of claim 34, wherein the inspectionentity is a non-governmental inspection entity.
 44. The method of claim43, wherein the inspection entity is an insurance company.
 45. Themethod of claim 43, wherein the inspection entity is the owner of theobject.
 46. The method of claim 34, wherein the jurisdictional entity isa governmental regulatory agency.
 47. The method of claim 34, whereinthe information regarding the inspectable object is accessible by thejurisdictional entity and by a plurality of nonjurisdictional entities.